Method, system, and program for accessing calendar information for shadowed users from a database

ABSTRACT

Provided is a method, system, and program for accessing calendar information of users in a database for presentation by a personal information manager. Scheduled event records for users are maintained within the database. Further maintained in the database is information on a current location of wireless devices of users in the database, wherein one user is associated with each wireless device. Scheduled event records and the current location of a wireless device for a shadowed user are provided from the database to a device operated by a shadower user in the database.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a method, system, and program for accessing calendar information for shadowed users from a database.

2. Description of the Related Art

Portable computing devices, such as hand held computers, cellular phones, palm devices, etc., have become increasingly popular in recent years. The technology has advanced to such a degree that now people can access the Internet through wireless technology, such as a cellular phone or personal digital assistant (PDA), and review content especially tailored for a small portable device. The term PDA, as used herein, refers to any wireless, portable, and small hand held computer device, such as a palm computer, cellular phone, wearable computers, etc. Some of the most popular mobile applications for such wireless devices have included personal information managers (PIMs), entertainment programs, financial services, and mobile commerce. One of the recent technological developments for mobile Internet access is the Wireless Application Protocol (WAP), which allows mobile devices to use data services and access the Internet. WAP provides a client/server architecture. A WAP enabled client, such as a cell phone or palm computer, can use micro browsers which are designed to operate within the small display screen of mobile devices and use less memory than a desktop browser. Content for mobile WAP enabled devices may be written in the Wireless Markup Language (WML), which provides a tagged mark-up language similar to the hypertext markup language (HTML), but designed specifically to function in a small-screen environment. Many content providers are providing WAP pages to enable access to the large base of mobile phone and PDA users.

Notwithstanding, recent developments in wireless computing, such as more advanced PIMs, Internet browsing and e-commerce features, only provide users with a significantly limited version of the programs and functions that are available at a desktop computer. For instance, a desktop PIM or calendar program provides a substantially more robust display presentation and range of program functionality than is available for mobile wireless device PIM applications. The same is true for Internet browsing. Given the substantial advantages of desktop PIM and Internet access programs over those available for mobile devices, most computer users, except the submarket of frequent business travelers, may not be motivated to purchase wireless devices for uses other than as a mobile telephone and limited PIM, e.g., address book, calendar, to do list, etc.

Thus, there is a need in the art for an application that would more fully exploit wireless computing technology to extend the utility beyond that of a portable telephone and limited PIM.

SUMMARY OF THE PREFERRED EMBODIMENTS

Provided is a method, system, and program for accessing calendar information of users in a database for presentation by a personal information manager. Scheduled event records are maintained for users within the database and information on shadowed events for a tracked entity is also maintained. Scheduled event records for a user and information on shadowed events of at least one tracked entity are provided from the data, wherein the scheduled event records are capable of being scheduled at calendar times that overlap with scheduled shadowed events for the at least one tracked entity. Information is displayed on the provided scheduled event records and shadowed events for a time period. A conflict signal is generated if scheduled event records for one user are scheduled for overlapping calendar times. The conflict signal is not generated if at least one shadowed event record and scheduled event record for which the information is displayed are scheduled for overlapping calendar times.

In further implementations, information is displayed on the shadowed events in a different manner than information on the scheduled event records for the time period is displayed.

Still further, user selection is received to add a selected shadowed event to the user scheduled event records and the selected shadowed event is added to the user scheduled event records.

Further provided is a method, system, and program for accessing calendar information of users in a database for presentation by a personal information manager. Scheduled event records for users are maintained within the database. Further maintained in the database is information on a current location of wireless devices of users in the database, wherein one user is associated with each wireless device. Scheduled event records and the current location of a wireless device for a shadowed user are provided from the database to a device operated by a shadower user in the database.

In further implementations, contact information indicating a communication channel to use to access the shadowed user is transmitted to a device operated by one shadower user. The device receiving the contact information is capable of using the contact information to access the shadowed user.

The described implementations allow database users to shadow the scheduled calendar events and monitor the current location of other users in the database. Further, contact information in the database may be provided to allow direct or indirect communication with the shadowed user.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers represents corresponding parts throughout:

FIG. 1 illustrates a telecommunication environment in which aspects of the invention are implemented;

FIG. 2 illustrates components of a PIM database in accordance with implementations of the present invention;

FIGS. 3 a, b, c, d illustrate data structures used in accordance with implementations of the present invention;

FIG. 4 illustrates further details of the telecommunication environment in which aspects of the invention are implemented;

FIGS. 5, 6, and 7 illustrate flowcharts of code logic to gather, process, and use location information in accordance with implementations of the present invention; and

FIGS. 8, 9 a, and 9 b illustrate examples of a display of user calendar and generated location information in accordance with implementations of the present invention.

FIGS. 10, 11, and 12 illustrate further examples of a display of a calendar including shadow calendar capabilities in accordance with implementations of the present invention;

FIGS. 13 and 14 illustrate further examples of a calendar including shadow capabilities in accordance with implementations of the invention;

FIG. 15 illustrates further records maintained for users in the PIM database in accordance with implementations of the present invention;

FIG. 16 illustrates a shadowed scheduled event record in accordance with implementations of the present invention;

FIG. 17 illustrates logic to provide database information on shadowed users in accordance with implementations of the present invention;

FIG. 18 illustrates logic to generate information on shadowed users in accordance with implementations of the present invention;

FIG. 19 illustrates a user interface to access a shadowed user in accordance with implementations of the present invention; and

FIG. 20 illustrates logic to provide contact information to access the shadowed user in accordance with implementations of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

In the following description, reference is made to the accompanying drawings which form a part hereof, and which illustrate several embodiments of the present invention. It is understood that other embodiments may be utilized and structural and operational changes may be made without departing from the scope of the present invention.

FIG. 1 illustrates a wireless computing environment in which embodiments of the invention are implemented. A wireless device 2, such as a telephony device, e.g., cellular phone, personal digital assistant (PDA), hand held computer, palm computer, etc., communicates with a server 4 via a communication tower 6, gateway server 8, and network 10. The server 4 may comprise one or more server class machines known in the art. The wireless device 2 includes a communication layer 12 which converts digital data into a signal that is transmitted to the communication tower 6 in a manner known in the art. The gateway server 8 converts the signals back into digital data to transmit via network 10 to the server 4. The network 10 may comprise any collection of devices, routers, etc. used to transmit data to a centralized server 4 providing data management for the wireless device 2 operations. The communication tower 6 and communication layer 12 may implement any known wireless transmission technology known in the art, such as 3G, Code-Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), satellite, Bluetooth, etc.** **Bluetooth is trademark of Telefonaktiebolaget LM Ericsson.

The wireless device 2 further includes locator technology 14 that provides a current position coordinate of the wireless device 2 in three dimensional space (x, y, z) on the surface of the earth and the time the position coordinate was generated. The locator 14 may comprise a global position satellite (GPS) receiver that is capable of calculating a current position based upon signals sent from satellites in a manner known in the art. Alternatively, the location of the wireless device 2 can be estimated externally from the wireless device by measuring the transmissions from the wireless device 2 using any known location positioning technology in a manner known in the art, such as Enhanced Observed Time Differential (E-OTD), Time Of Arrival (TOA), the CellPoint positioning system, the Ericsson Mobile Positioning System, etc.** In fact the United States Federal Communication Commission (FCC) mandated that cellular phone manufacturers incorporate technology to allow the location of the wireless device 2 to be determined. Any reference to the locator 14 refers to the locator technology used within the wireless device 2 that enables a position determination. For instance, if the locator 14 comprises a GPS receiver, then the locator 14 itself may determine the actual position coordinate. Alternatively, the locator 14 may provide information to an external component to enable the external component to determine the position coordinate of the wireless device 2.

The wireless device 2 further includes an input mechanism 16 for entering any type of data, including text, voice data, audio, images, movies, etc. The input mechanism 16 may include any known data input system known in the art, including a keyboard embedded in the device 2 with depressable keys, a touch sensitive displayed keyboard, a microphone for providing audio input, voice recognition software, still image camera, video recorder, pen-stylus text input system including handwriting recognition software, etc. Data entered by the user through the input mechanism 16 or downloaded from the server 4 can be rendered in display 18, which may comprise any electronic display device known in the art. A Personal Information Manager (PIM) client 20 gathers and presents PIM information, such as calendering and scheduling information, in accordance with the described implementations. The term “PIM” as used herein refers to a program designed to allow users to organize random bits of information in a useful format. The PIM program may enable calendar or scheduler operations. A calendar program enables one or more users to record and organize events and appointments. A scheduler program enables a group of colleagues to schedule meetings and other appointments, and share schedule and calendar information. Further, the PIM may be intended for use by a single individual for personal information or for use by a company or organization to provide information related to that persons involvement with the company or organization. The use of the term PIM or PIM program herein refers to any program that includes some or all of the above described calendar or scheduler functions, or any other f unctions those skilled in the art associate with PIMs.

The server 4 includes a PIM database 22 maintaining user PIM information and a PIM server 24 for gathering and filtering data from wireless devices 2 for the users of the system. The PIM database 22 may be implemented using any database technology known in the art, e.g., relational database, object oriented database, etc. Although FIG. 1 only shows one wireless devices 2, the server 4 and PIM database 22 may maintain data for multiple wireless devices 2 and users.

In the described implementations, the PIM client 20 gathers position coordinates for the PIM server 24. The PIM server 24 then uses the position coordinates to supplement the user calendar records with information on what the user actually did for time periods within a day. The user could then view this enhanced calender including listings of scheduled appointments as well as information describing the actual location and activities of the user and descriptions thereof. The term “location” and “geographic location” as used herein refer to any location that may be mapped and ascertained. Such location or geographic location may be any location on the surface of the earth or the earth's atmosphere, or outer space, that can be expressed as a position coordinate in space. The term “location” or “geographic location” may refer to a specific position coordinate in space, e.g., an X, Y, Z coordinate, or a boundary or area of coordinates. Additionally, the location may be expressed as a vector. The term “position coordinate” as used herein refers to any of a set of numbers used in specifying the location of a point in space, or any one of a set of variables used in specifying the state or motion of an entity, such as a wireless unit or person, associated with the position coordinate.

The PIM server 24 includes the program logic that responds to data requests from PIM clients 20, accesses the PIM database 22 to perform database operations, and performs other data management operations related to managing the PIM database 22. The PIM server 24 may include a database management system (DBMS) known in the art or include an interface to access a DBMS program in a manner known in the art to perform operations with respect to the PIM database 22. The PIM server 24 may implement any database programming techniques for performing operations in the PIM database 22. For instance, the PIM server 24 may implement separate application programs for performing database operations or implement database stored procedures to perform database operations. The PIM client 20 includes those program components that gather coordinate and location information as described herein, communicates with the PIM server 24, and renders calendaring information at the wireless device 2.

FIG. 2 illustrates the data components of the PIM database 22 maintained by the server 4. The PIM database 22 includes a plurality of user records 50 for each user of a wireless device 2 participating in the wireless computing environment described herein. Each user record 50 includes one or more user scheduled event records 52, measured position records 54, and location records 56 and 58. From the measured position records 54, the PIM server 24 generates filtered position records 60 that provide information on user geographic location and activity for time periods, such as information for a period of fifteen minutes, twenty minutes, one hour, etc.

FIG. 3 a illustrates fields in a user scheduled event record 52, including a date 70, time period 72 indicating a time range of the event, and a scheduled event description 74 providing information on the nature of the scheduled event. Through the client PIM 20 software, a user could use the input mechanism 16 to schedule a calendar event and create a scheduled event record 52. Additionally, the user could enter scheduled events from a desktop computer (not shown) that communicates with the server 4 via a network such as the Internet. The scheduled events may be shown in a calendar rendered on the display 18. Additionally, the scheduled events may be shown in a calendar rendered on another computer capable of accessing the server user records 50 in the server 4, such as a desktop computer communicating with the server 4 over the Internet.

FIG. 3 b illustrates fields in a measured positioned record 54 for a user, including a date 80 and time 82 the position was measured, a position coordinate 84 expressed as a unique three dimensional x, y, z geographic coordinate on the surface of the earth, and a location description 86 providing descriptive information on the location. In the described implementations, the PIM client 20 periodically generates a measured position record 54 by obtaining the measured position coordinate (x, y, z) and the current time from the locator 14 (which may, in certain implementation interact with external components to provide the location and position coordinate). The location description 86 may be obtained locally at the wireless device 2 or determined subsequently by the server 4 as described in the following implementations.

FIG. 3 c illustrates the fields maintained in the user defined 56 and public 58 location records. An access level field 90 indicates which users can be allowed to use the location record 56 or 58 to determine information about a location. The public location record 58 has public level access such that the PIM server 24 can consider a public location record 58 for any user in the PIM database 22. A user location record 56 can only be considered for the particular user that defined the location record 58 and any other authorized users in the system, as indicated by the access level 90. A geographic boundary field 92 defines a boundary of a defined region in three dimensional space. A location description field 94 provides a description of the location, which may include text, images, sound, movies, etc. A company maintaining the server 4, such as a telecommunication service provider, can use satellite maps and other information to determine the geographic boundaries in three dimensional space of various buildings and businesses. Business could register their geographic boundaries. Public location records 58 may then be generated for each of these determined geographic boundaries and include a description of the location within the geographic boundary.

The user specified location records 56 are generated by the user to provide information to include with the user's calendar. For instance, the user may obtain from a third party, such as a mapping company or organization, the geographic boundaries of an office or building and provide geographic boundary and location description information to the server 4 to include in a user location record 56. In another implementation, the user can activate a geographic boundary definition mode on the wireless device 2 to record position coordinates of a geographic boundary using the locator 14. In this geographic boundary definition mode, the user may walk or otherwise travel around a geographic area. While moving through the geographic area, the wireless device 2 would determine the x, y, z position coordinates at frequent intervals using the locator 14. The PIM client 20 or PIM server 24 can then use the determined position coordinates to determine a geographic boundary bounding all of the coordinates generated in the geographic boundary definition mode. This determined geographic boundary would then be included in the geographic boundary field 92 of the eventual user defined location record 56 stored in the user records 50 in the database 22. The user may further use the input mechanism 16 to enter information to include in the location description field 94 and the access level 90. The user access level 90 may specify that the user location record 68 be accessible to the user and other specified users, thereby limiting access of the location record 56 to a user defined group.

FIG. 3 d illustrates a filtered position record 60 generated from a range of consecutive position records 54 having a same location description 86. The date range 100 and time range 102 for the generated filtered position record 60 would comprise the first and last dates 80 and times 82 of the consecutive position records 64 having the same location description 86. In this way, a single filtered position record 60 represents the data in multiple consecutive position records 54 having a same location description 106. Alternatively, a filtered position record 60 can consolidate multiple position records 54 that have position coordinates 84 within a predetermined proximity, without consideration of the location description 86. A geographic location field 104 indicates the common geographic location of the position records 60 having the same location description 86, which could include the geographic boundary from a location record 56 or 58 if the location description 86 of the consolidated position records 60 was determined from a location record 56 or 58.

Additionally, if algorithms in the PIM server 24 determine that a range of measured position records 54 define an activity, e.g., driving, walking, flying in an airplane, etc., then a filtered position record 60 would be generated for those position records 54 defining the activity. The date range 100 and time range 102 for the generated filtered position record 60 would comprise the first and last date 80 and time 82 of the consecutive position records 64 defining an activity and the location/activity description 106 field for this filtered position record 60 would include a description of the determined activity.

FIG. 4 illustrates an additional implementation of the telecommunication environment for obtaining geographic boundary information. A location transmitter 110 is maintained in a geographic location or boundary 112, such as an office, building, designated region, etc., and includes a communication layer 114 to transmit data throughout the geographic location 112. For larger geographic locations, multiple location transmitters 110 may be deployed to transmit throughout the entire geographic location 112. The location transmitter 110 maintains a geographical boundary 116, defining a region of x, y, z coordinates, and a location description 118 providing descriptive information on the geographic boundary 112. The local transmitter 110 is capable of transmitting the geographic boundary 116 and location description 118 through the communication layer 114 to any receiving device within the geographic boundary 102. For instance, the communication layers 12 and 114 of the wireless device 2 and location transmitter 110, respectively, may implement Bluetooth technology. In such Bluetooth implementations, the location transmitter 110 may continually transmit packets containing an Inquiry Access Code (IAC) to establish communication with any wireless devices 2 within the geographic boundary 112. The wireless device 2 may then respond to establish a connection with the local transmitter 110. Upon establishing the connection, the local transmitter 110 may then transmit the geographic boundary 116 and location description 118 through communication layer 114 to the communication layer 12 of the wireless device 2. Further details of Bluetooth communication technology are described in the publication “Bluetooth(™): Connect Without Cables” by Jennifer Bray and Charles F. Sturman (Copyright 2001, Prentice Hall), which publication is incorporated herein by reference in its entirety. In alternative implementations, the communication layers 12 and 114 may utilize wireless communication protocols other than Bluetooth known in the art to perform the communication operations described herein, such as the wireless LAN architecture standard proposed in IEEE 802.11.

FIGS. 5-7 illustrate logic implemented in the PIM client 20 and server 24 to gather and utilize position information concerning the wireless device 2. FIG. 5 illustrates logic implemented in the PIM client 20 to gather position information to provide to the PIM server 24 to include within measured position records 54 in the database 22. At block 200, the wireless device 2 establishes communication with a location transmitter 110, using the Bluetooth technology or other wireless technology known in the art. After establishing a connection with the location transmitter 110, the PIM client receives (at block 202) a geographic boundary 116 comprised of X, Y, Z coordinates defining a three dimensional boundary on earth and location information describing the geographic boundary 116.

To provide data to the PIM server 24, the PIM client 20 performs steps 250 through 264 in interval time periods, e.g., every few seconds, minute, etc., to measure the current location and generate measured position records 54. At block 250, the PIM client initiates a location request to the locator 14 or other unit to determine the current position coordinate (x, y, z) of the wireless device 2. Upon receiving (at block 252) the position coordinate from the locator 14, the PIM client 20 determines (at block 254) whether the received position coordinate falls within any predefined geographic boundaries supplied by a location transmitter 110, the PIM server 24, a user defined location record 56, or any other geographical boundary maintained by the PIM client 20. If so, the PIM client 20 generates (at block 256) data for a measured position record 54, including the received position coordinate, the date and time the coordinate was determined, and any location description associated with the predefined geographic boundary including the received position coordinate. The gathered data is then sent (at block 258) to the PIM server 24 to include as a position record 54 in the user records 50.

If (at block 254) the received position coordinate did not fall within any predefined geographic boundary, then the PIM client 20 generates (at block 260) data for a measured position record 54 including the received X, Y, Z position coordinate and the date and time the coordinate was measured. If (at block 262) the user has entered through the input mechanism 16 any location description for the current location through the input mechanism 16, then the PIM client 20 adds (at block 264) the user specified location description to the data for the measured position record. From block 264 or the no branch of block 262, the PIM client 20 transmits the data for the measured position record 54 to the PIM server 24 to include in the user records 50.

FIG. 5 provides logic implemented in the PIM client 20 to gather the position records for each measured coordinate. FIG. 6 illustrates logic for a filtering algorithm that consolidates and interprets the measured position records 54 and generates filtered position records 60 that provide information on the user's whereabouts and activities for time periods. The filtering algorithms used to generate the filtered position records 60 may be implemented in either the PIM client 20 or PIM server 24. In the event that the PIM client 20 executes the filtering algorithm, then the PIM client 20 would transmit the filtered position records 60 to the PIM server 54 to store in the PIM database 22.

With respect to FIG. 6, control begins at block 300 with the invocation of the filtering algorithm for the user records 50 of a particular user. A loop is performed from blocks 302 to 314 for each measured position record i in the user records 50 that has not yet been subject to filtering to add location description information 86 to the measured position record 64 if such data was not provided by the PIM client 20. If (at block 304) the measured position record i does not include any location description 86 data, then a determination is made (at block 306) as to whether the position coordinate 84 data in record i is within the geographic boundary of any user defined location records 56 of the user being considered. If so, then the location description 94 for the user defined location record 90 is added (at block 308) to the location description 86 data for the measured position record 64. If (at block 306) a geographic boundary was not located in the user defined location records 56, then a determination is made (at block 310) whether the position coordinate 84 data in record i is within the geographic boundary of any public location records 58. If so, then the location description 94 for the public location record 58 is added (at block 312) to the location description 86 data for the measured position record 64. From the yes branch of block 304 (if there is already location information added by the PIM client 20) or from blocks 308 or 312, control proceeds to block 314 to consider all the measured position records 54 for the user. The related application entitled “Method, System, and Program for Providing User Location Information for a Personal Information Management System”, which is incorporated by reference in its entirety above, provides additional implementations for obtaining location description information from the user records for other entities and persons in the PIM database 22.

After the measured position records 64 are supplemented with location information from user defined 56 or public 58 location records, then control proceeds to blocks 316 to generate the filtered position records 60 that are particularly suited for use in a PIM or calendaring program. At block 316, the filter scans from the first user position record 54 to determine ranges of consecutive position records 54 having the same location description 86 spanning a time period exceeding a minimum time period. Thus, the filter is looking for position records indicating that the user was at a same location for a minimum time. The minimum time may be a time period of sufficient length that would be meaningful to display in a PIM interface, such as a calendar or schedule, e.g., 10 minutes, etc. For each determined range of records, a filtered position record 60 is generated (at block 318) having a date 100 and time 102 ranges from the date and time of the first to last position records in the determined range and having a location description 106 that is the common location description 86 found in the position records 54 in the determined range. In this way, a single filter position record 50 is generated that defines a location position that was maintained for a minimum time.

At block 320, activity algorithms may then be applied to those position records not consolidated into filtered position records 58 at block 316 and 318. An activity algorithm would analyze a series of consecutive measured position records and based on a rate of change in distance per unit of time, determine a predefined activity associated with the position records. For instance, a range of consecutive measured position records 54 whose position coordinate 84 (x, y, z) is rapidly changing may indicate that the user is traveling in an automobile or other transportation vehicle. Other rate of changes may indicate other activities, e.g., walking, running, bicycle riding, etc. For each determined range of measured position records 54 that define an activity, a filtered position record 60 is generated (at block 322) having a date 100 and time 102 ranges from the date 80 and time 82 of the first and last measured position records 54 in the range and an activity description field 106 set to the activity determined for the range. The geographic location field 104 may comprise a range of first and last locations for the activity, wherein the first location would comprise the location 84 data from the first measured position record 64 in the range for the activity and the last location would comprise the location data 84 from the last record 84 in the range. Thus, in certain described implementations, a filtered position record 60 indicates a time period during which a user was at a location, defined by a geographic boundary or a time period during which the user was engaged in an activity involving movement from one location to another.

The filtered position records 60 are then stored (at block 324) in the PIM database 22 for later use. The filtered position records 60 provide more useful descriptive information than the measured position records 54 because they indicate time periods spent at meaningful geographic locations or engagement in a particular activity.

FIG. 7 illustrates logic implemented in the PIM server 24 to generate calendar information that can be displayed at the wireless device 2 or some other computer in communication with the server 4, such as a desktop computer accessing the server 4 over the Internet. Control begins at block 350 with a request for PIM information for a time interval for a user. In response, the PIM server 24 queries the PIM database 22 for filtered position records 60 (at block 354) and scheduled event records 52 (at block 356) of the user within the specified time interval. The PIM server 24 then generates (at block 358) for each calendar time period, e.g., every half-hour, hour, etc., information on the scheduled event description 74 and the location/activity description 106 (FIGS. 3 a, d) in the located scheduled event 52 and filtered position 58 records, respectively, that fall within the calendar time periods that span the specified time interval.

If (at block 360) the viewer program requesting the calendar information for the time period is a WML browser on a small device, e.g., the wireless device 2, then the PIM server 24 generates (at block 362) one or more WML pages including a presentation of the information generated for each calendar time period in the user specified time interval including information on user scheduled events and actual location/activity. Otherwise, if the viewer or browser requesting the calendar information includes a larger display area, then the PIM server 24 generates (at block 364) one or more HTML pages including the presentation of the generated calendar information. From blocks 362 or 364, control transfers to block 366 to transmit the generated web pages to the browser requesting that page. Alternatively, the PIM server 24 may include the generated calendar information in an Extensible Markup Language (XML) or other file that is sent to the PIM client 20 to render on the local display. Thus, the calendar information presented to the user may include a description of user scheduled events as well as information on the geographical locations the user associated with the wireless device 2 visited during the specified time interval.

FIG. 8 illustrates an example of calendar information for the user specified time period presented in a calendar window 400 rendered on a computer display monitor. As shown, the calendar displays both user scheduled events 402 from the scheduled event records and actual location/activity 404 from the filtered position records for calendar times 406 during the specified time interval. In this way, the user may compare what was scheduled with what actually materialized. Moreover, in implementations where the PIM server 24 updates the user calender information in real time and generates real time filtered position records, the calendar 400 could display the user's current geographical location. This information could be useful for business associates and others interested in the user's location. Additionally, the actual location/activity 402 may be displayed in an abbreviated format. The user may use an input device to selectively display further details on the actual location/activity. For instance, the user may move a mouse input device over the displayed abbreviation of the actual location/activity or click the displayed abbreviation to cause the display of more detailed information on the actual location/activity in the calendar window 400.

FIGS. 9 a, b illustrate how calendar information may be displayed on a display 18 of a wireless device 2 having limited display space. FIG. 9 a illustrates a small displayed monthly calendar. Upon user selection through the input mechanism 18 of a particular day, e.g., February 5^(th), the PIM client 20 displays the view shown in FIG. 9 b which provides information of scheduled events 450 and actual user location/activity 452 for a portion of the calendar times 454 during the user requested time interval. The user can use the input mechanism 18 to scroll downward to view further calendar entries.

The described implementations provide a technique for gathering and utilizing user position information for use with a PIM or calendaring program. This position information may be provided to the user and those authorized by the user to track actual activity versus scheduled activity.

Shadowing Calendar Events

In certain implementations, the personal information management system may include the capability to allow users having user records 50 in the database to shadow the schedule or location of other users in the system, so that a user can view user records 50 of another user or entity. FIG. 10 illustrates a calendar including the features described with respect to FIG. 8 and additionally including three tabs 468 a, b, c. Selection of tab 468 a causes the display of the user's own personal calendar as shown in FIG. 10. Tabs 468 b and c provide displays of shadow calendars, to allow the user to view scheduled activities and current actual location of another user, e.g., the “spouse”, and the scheduled events of an organization, e.g., the Austin philharmonic. FIG. 11 illustrates the shadow calendar schedule of the spouse displayed in response to user selection of the “Shadow Spouse” tab 468 b, including the current location of the wireless device 2 used by the shadowed spouse. In this way, the user may view the schedule of another shadowed user, including the current location of their wireless device 2. The schedule of the shadowed person could also display an actual activity column 402 as shown in FIG. 8.

FIG. 12 illustrates the shadow schedule of events for an organization, which in the example is the Austin philharmonic, that is displayed in response to user selection of the “Austin Philharmonic” tab 468 c. An organization's shadow schedule would display events sponsored by the organization, such as a concert performance by the Austin philharmonic.

FIG. 13 illustrates an additional implementation of the user calender where the shadowed schedule of events is displayed as transparent text 484 superimposed onto the calendar, such as the transparent “Beethoven Concert”. The user may select a function key or other control to display shadowed events as superimposed transparencies over the user schedule, and turn on and off the display of the transparent shadowed schedule of events. These above display mechanisms display the shadowed schedule of events as “optional events” that the user may selectively add to the regular scheduled event records 52 (FIG. 3 a) that are displayed as regular scheduled events. In this way, the shadowed events are not “hardened” scheduled events. Further, the shadowed schedule of events would not appear as user scheduled events when others view the user calendar, but only become hardened scheduled events if the user selects to add shadowed events to the user schedule by converting the shadowed event to a scheduled event record 52 in the user records 50.

Selection of the shadowed event may display dialog box 490 shown in FIG. 14 which displays further information on the shadowed event as well as a button 492 to allow the user to add the shadow event to the user scheduled event records 52 to be displayed as a regular scheduled event.

Morever, in certain implementations, the shadowed event does not override or conflict with a regular user scheduled event record 52. For instance if a user schedules two user events at the same time, for which separate scheduled event records 52 would be created, then a conflict signal may be generated notifying the user of the conflicting scheduled events. However, for shadowed events, if the shadowed event is scheduled at the same time as a regular user scheduled event, then the shadowed event may be displayed as a transparency over the regular scheduled event, as shown as the transparent text 486 in FIG. 13. In such case, no conflict signal would be generated indicating an attempt to schedule conflicting appointments because the shadowed event is an event from another entity the user is monitoring and is not considered an event the user is adding to their own schedule. The user may select to accept or “harden” the shadowed event, which would transform the shadowed event into a user scheduled event record 52. User selection to harden the shadowed event into a regularly scheduled event may override any previous scheduled event for that time slot.

The user may select users to shadow to view their scheduled event records 52. However, permissions may need to be granted to shadow an individual, whereas organizations, such as businesses, may allow any data base user to shadow scheduled events. For instance, a business may schedule sales, promotions, and other commercial related events that a database user can shadow in their calendar.

FIG. 15 illustrates further details of data structures included in the user records 50 to implement shadowing. The user records 50 would include the data structures shown in FIG. 2 and additionally include a tracking list 500, shadowed scheduled event records 502, and a user profile 503 (FIG. 15). In one implementation, to allow users to shadow other calenders or scheduled event records 52 of other users, the user records 50 of those whose schedule is being shadowed would include a tracking list 500 providing a unique identifier of those users registered to track the calendar events of others. Further, the user records 50 of those users tracking other users', i.e., tracking users, scheduled events would include one or more shadowed scheduled event records 502. A user profile record 503 includes descriptive information on the user associated with the user records 50, such as a unique identifier, contact information to communicate with the user via the wireless device 2 or a separate communication device, e.g., telephone numbers, e-mail, chat identifier, pager, etc.

In certain implementations, the user records 50 would maintain one shadowed scheduled event record 502 for each shadowed user. FIG. 16 illustrates an implementation of a scheduled event record 502 where each scheduled event record 502 includes all the data for one shadowed user. A shadow calendar number 502 comprises a unique number assigned to each scheduled event record to identify the scheduled event record in the user records 50. Shadowed user information 504 provides the unique identifier of the user in the PIM database 22 being shadowed, descriptive information 506 on the shadowed user, such as contact information, etc. A most recent measured position record 508 comprises the most recent measured position record 54 (FIGS. 2, 3 b) of the shadowed user that is used to provide information on the current location of the shadowed user. Following are one or more scheduled event records 510 a . . . n of the shadowed user, which may comprise the scheduled event records 52 to be displayed in the tracking user's calendar, where the tracking user is the user registered in the tracker list 500 who views or tracks another's scheduled events and location information. The scheduled event records 510 a . . . n may include the date, time period, and description for the scheduled event, as shown in FIG. 3 a. In alternative implementations, the shadowed scheduled event records 502 may be maintained in one location of the database 22 and the tracking user records would include a pointer to the shadowed scheduled event records.

In the above described implementations, the shadowed scheduled event records 502 are maintained with the tracking user records 50 in the PIM database 22. Alternatively, the shadowed scheduled event records 502 may be maintained locally in the wireless device 2 of the tacker for use by the PIM client 20 in rendering the shadowed calendar information in response to selection of the shadow tabs 468 a, b (FIGS. 10, 11, and 12). In such alternative implementations, the shadowed scheduled event records 502 would not be stored in the tracking user records 50 in the PIM database 22 as shown in FIG. 13.

FIG. 17 illustrates logic implemented in the PIM server 24 to push shadowed scheduled events to the user records 50, or wireless devices 2, of tracking users. The process to push shadowed scheduled event records beginning at block 550 may be performed periodically or in response to an update to one of the scheduled event records 50 of the shadowed user or to adding a new user to the tracking list 500. Blocks 552 to 560 comprises a loop performed for each user i listed in the tracking list 500. At block 554, the PIM server 24 determines whether there is a shadowed scheduled event record 502 for the shadowed user in the user records 50. If not, then the PIM server 24 creates (at block 556) a new shadowed scheduled event record 502 in the user records 50 of user i, including a shadowed calendar number 504 and shadowed user info 506. From the yes branch of block 554 or 556, the PIM server 24 adds (at block 558) shadowed user scheduled event records 50 for a time interval to the shadowed scheduled event record 502 of the tracking user records 50. As discussed, in alternative implementations, the PIM server 24 may communicate the shadowed scheduled event records 502 to the tracking user's wireless device 2, and not maintain a copy in the tracking user records 50. The PIM server 24 would further determine (at block 560) the measured position record 54 in the shadowed user records 50 having the most recent date 80 and time 82, and add the determined measured position record 54 to the most recent measured position record 508 in the shadowed scheduled event record 502 of the tracking user. The PIM server 24 performs (at block 562) another iteration of the loop beginning at block 552 for the next tracking user in the tracking list 500 shadowing the scheduled event records.

With the logic of FIG. 17, the PIM server 24 pushes data from shadowed user records to the tracking user records 50 or wireless device 2. The PIM server 24 would perform the logic of FIG. 17 for every user in the PIM database 22 whose user records 50 include a tracking list 500. In alternative implementations, the PIM client 20 may pull the shadowed scheduled events and other information from the shadowed user records 50 in the PIM database 22 on an as needed basis when the tracking user of the wireless device 2 selects one of the shadow tabs 408 b, c to display a shadowed calendar.

FIG. 18 illustrates logic implemented in the PIM client 20 to display shadowed scheduled event records on the display 18 of the wireless device 2 (FIG. 1) as shown with respect to FIGS. 11 and 12. At block 580, the PIM client 20 receives user selection of one of the shadow tabs 408 b, c. In response, the PIM client 20 accesses (at block 582) the shadowed scheduled event record 502 corresponding to the selected tab 408 b, c. The database 22 may maintain a mapping of displayed tabs to shadowed scheduled event records 502 using the shadow calender number 504. The PIM client 20 then generates (at block 584) a calendar display on the display 18, such as shown in FIGS. 11 and 12, displaying the scheduled events for a time interval. A determination is made (at block 586) of the displayed calendar time period including the time of the most recent measured position 508. The PIM client 20 then displays (at block 588) the location description 86 from the determined most recent measured position record 508 in the determined period to show the real time location of the user in the calendar display, such as the real time location 410 displayed in the calendar shown in FIG. 11.

The logic of FIG. 18 allows a user to separately view scheduled events of shadowed users or entities. Alternatively, the scheduled events of different shadowed users may be displayed on the same calendar page showing shadowed scheduled events from different users.

In further implementations, the location information displayed in the shadowed calendar window, e.g., location information 472 (FIG. 11), may comprise a hypertext link to allow a user to access further information on the displayed location of the shadowed users. Further, the displayed shadowed scheduled events in the calendar windows may also comprise hypertext links. For instance, if the shadowed entity comprises a business or organization, then the hypertext link of the scheduled event for the organization, such as a scheduled concert, sporting event, etc., may be selected to access further information on the scheduled event. For instance, if the business entity promoting the shadowed events is selling access or seats to the event, such as sporting events, theatrical productions, concerts, etc., then selection of a hypertext link description of the event may cause the PIM client 20 to display a window in which the user may purchase tickets for an event, reserve seats, etc.

In additional implementations, the PIM client 2 and PIM server 24 may include the capability to allow the user viewing shadowed events to contact or obtain information on the shadowed user. For instance, the current location of a shadowed user may be displayed in the shadow calendar as a hypertext link, as the current location 400 shown in FIG. 11. Selection of the hypertext link of the current location 472 or some other interface button on the calendar window of FIG. 11 may display a communication window 600 shown in FIG. 19 on the display 18 of the wireless device 2 (FIG. 1). The displayed communication window 600 may include a direct communication drop down list 602 which allows the user to select an available channel to use to communicate directly with the shadowed user, such as a phone, e-mail, pager, on line chat, etc. The available channel may allow direct communication with the wireless device 2 of the shadowed user or communication with a separate device possessed by the shadowed user. Selection of one of the communication channels through the drop down list 602 and the GO button 604 would provide further information on the communication channel or invoke the selected communication technique through the tracking user's wireless device 2. For instance, if the wireless device 2 is a telephony device, then selection of the GO button 604 may dial the shadowed user's phone number, send an e-mail, call the shadowed user's pager, establish a chat session, etc. In this way, through the shadowing feature, a user may not only view the shadowed user's current location, but also establish direct communication with the shadowed user.

The communication window 600 further includes a proximate device drop down list 610 through which the user may establish communication through a third party proximate device having user records in the database. For instance, drop down menu 610 lists communication channels with users within a proximate distance from the shadowed user that may be invoked to communicate with the proximate user. In this way, the user may communicate with a proximate user about the shadowed user. Still further, the proximate user may comprise a location transmitter 110 (FIG. 4) that streams real time video from the current location of the shadowed user. If so, then the user may use the drop down menu 610 to select the location transmitter 110 to access real time video from the location to view the shadowed user at the location through the display 18 of the wireless device 2.

The video aspect could be particularly useful for parents who want to observe their young children at day care or school. If the child carries a wireless device 2 and is a shadowed user and the child care or school includes a location transmitter 110 providing real time video streaming, then the user may use the drop down menu 610 to select the school location transmitter 110 to access streaming real time video of the location including their child. Further, a school or day care may include location transmitters 110 at numerous locations, within classrooms, in the play yard, lunch room, etc., to allow a parent to view a shadowed child at their specific location in the school.

The user of the device receiving the information to use to contact a proximate user, transmitter location 110 or the shadowed user directly may use the device including the PIM client 20 to communicate or use another device separate from the device including the PIM client 20.

Further, a company may charge a fee to users for the privilege to shadow the schedule of a famous person, such as an entertainer, sports figure, etc. Users may further be allowed to view real time video of the shadowed user. The company may charge different levels of fees to access real time video from location transmitters 110. For instance, if you pay one fee you may just obtain shadowed calendar entries of the famous person. If you pay a further fee, you may be permitted access to the real time video capabilities of location transmitters 110 placed in spaces that the famous person visits, such as a gym, clubs, restaurants, galas, etc. Further, politicians may allow users to shadow their schedule and permit viewers to view real time video of the politician when attending public spaces including a location transmitter 110 with real time video streaming capabilities.

FIG. 20 illustrates logic implemented in the PIM client 20 and PIM server 24 to provide the communication channel information to use to populate the drop down lists 602 and 610 shown in FIG. 19. Blocks 650 to 656 illustrates logic performed by the PIM client 20 in response to receiving user selection of the communication window 600 (FIG. 16) at block 650. The PIM client 20 determines (at block 652) from the shadowed user information 506 (FIG. 14), the available communication channels for the shadowed user. As discussed, the shadowed user information 506 maintains user profile information on the shadowed user, which in certain implementations includes contact information, such as phone numbers, pager number, e-mail address, chat contact information, etc. The PIM client 20 then displays (at block 654) the determined communication channels in the direct communication drop down list 602 (FIG. 19) as selectable items. The PIM client 20 sends (at block 656) a request to the PIM server 24 for contact information for users and entities within a proximate distance from the shadowed user's current location included in the most recent measured position record 508 (FIG. 16).

In response to receiving (at block 660) the request for proximate user and entity contact information, the PIM server 24 performs blocks 662 to 668. At block 662, the PIM server 24 queries the user records 50 for all users in the PIM database 22 to determine those users whose most recent measured position record 54 (FIG. 3 b), having the most recent date 80 and time 82, have a position coordinate 84 within a predetermined distance from the current position of the shadowed user. The PIM server 24 further queries (at block 664) the PIM database 22 for all location transmitters 110 (FIG. 4) having a geographic boundary 116 including the current position of the shadowed user. In certain implementations, the PIM database 22 may maintain user records 50 for location transmitters 110 to allow calendars to be generated for location transmitters 110 providing calendar information for the location associated with the location transmitter 110, e.g., the building, room, vehicle, etc. associated with the location transmitter 110. Such location transmitter 110 user records 50 may further include user profile 503 information that indicates the geographic boundary of coordinates associated with the location transmitter 110 and any remote communication capabilities at the location transmitter 110, such as video streaming capabilities, telephones, etc. The PIM server 24 then determines (at block 666) available communication channels for all the determined proximate users and location transmitters 110 and transmits (at block 668) the information on available communication channels to the PIM client 20.

In response (at block 680) to receiving the available communication channels from proximate users and location transmitters 110, the PIM client 20 displays (at block 682) a selectable description of each available communication channel in the proximate device drop down list 610 (FIG. 18).

The described implementations extend the PIM technology of the described implementations to allow users in the PIM database 22 to shadow the scheduled calendar events of other users in the PIM database 22 and monitor their current location. Further capabilities include access to direct or indirect communication channels to contact or observe the shadowed user.

Additional Implementation Details

The described aspects of the invention, including the logic described with respect to the PIM client and server and any other devices, may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. The term “article of manufacture” as used herein refers to code or logic implemented in hardware logic (e.g., an integrated circuit chip, Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), etc.) or a computer readable medium (e.g., magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, firmware, programmable logic, etc.). Code in the computer readable medium is accessed and executed by a processor. The code in which the invention is implemented may further be accessible through a transmission media or from a file server over a network. In such cases, the article of manufacture in which the code is implemented may comprise a transmission media, such as a network transmission line, wireless transmission media, signals propagating through space, radio waves, infrared signals, etc. Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope of the present invention, and that the article of manufacture may comprise any information bearing medium known in the art.

In the described implementations, the wireless device obtains the position coordinates and time and date information and transmits the data to the server 4. In alternative implementations, telecommunication devices or towers can detect the location of the wireless device and transmit the data for the measured position record 54 directly to the server 4. In such implementations, the wireless device would not be involved in transmitting position coordinates for the measured position records.

The described implementations concerned maintaining user location information with a user calendar program. The described implementations can further be used to provide and utilize a persons geographic location and/or activities for a measured time period for any purpose, not just calendering. For instance, a company may want to track the location and activity of workers. The company can then filter and compare a workers actual location/activity with their work schedule. Such information would be particularly useful for manufacturers and others attempting to determine optimal human resource allocation in the workplace.

The PIM location/activity information of the described implementations would also be very useful for companies that have to send workers out to field locations, such as cable companies, telephone companies, plumbers, etc., to track how the worker's actual location/activities correspond to those scheduled. In the case that real time worker location/activity information is provided to the calendar display, then the company can track the workers schedule and their actual geographic location in real time. Moreover, because descriptive geographic information is provided, a quick review of the calendar information can provide useful information on the workers geographic location, such as their presence in a particular building. Moreover, to the extent location records define the geographic boundaries of major roadways and freeways, a manager could review a field workers real time calendar, which could display that the worker is presently driving on a roadway. The activity algorithm can specify the rate the worker is traveling, i.e., indicating stuck in traffic, etc.

In the described implementations, scheduled events and location/activity information were displayed together in a user calendar view. Alternatively, the calendar view may selectively display only scheduled events or location/activity information.

The described implementations presented the scheduled event and location/activity information at different times during a user specified time interval. However, the generated location/activity information may be presented in alternative formats. For instance, the user may generate a display of all locations visited and activities, and the time period during which the location was visited or activity performed would be displayed under the location/activity display.

FIGS. 3 a, b, c, d illustrate one implementation of the data structures used to maintain the information used in the described implementations. However, those skilled in the art will recognize that the there are numerous ways the data shown in FIGS. 3 a, b, c, d may be organized in data structures and a database for storage and retrieval.

In the described implementations, the PIM server 24 transmitted the PIM information to the client PIM 20 or some other client to display in a browser, such as a WML or HTML browser. In alternative implementations, the PIM server 24 may provide the generated PIM information in alternative presentation and file formats, or alternative text markup languages than those described herein. Moreover, the location information presented to the user through the browser may present information in alternative presentation formats, such as audio, movies, etc. For instance, the calendar may display a hypertext description of the visited location. User selection of the hypertext description could present a movie or audio file about the visited location.

Still further, the user, through the wireless device 2 or some other computer may provide images or audio files taken from a location to associate with measured position records. In certain implementations, the wireless device 2 could include a microphone, still image camera, video camera etc. The user could then associate such multi-media files image information with the location that the PIM client 20 would provide with the measured position records 54 sent to the PIM server 24. This information would be made available to those viewing the calendar providing the location/activity information.

In the described implementation, the generated location was expressed as an x, y, z position coordinate. However, as discussed, the position coordinate may be expressed as any set of numbers used in specifying a location in space, or may comprise a code or descriptor defining a location in space.

The foregoing description of the preferred embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended. 

1. A method for accessing calendar information of users in a database for presentation by a personal information manager, comprising: maintaining scheduled event records for users within the database, including a given user; maintaining information for the given user on shadowed events for a tracked entity that are part of the tracked entity's scheduled event records, wherein the tracked entity was selected by the given user; providing from the database scheduled event records for the given user and information on shadowed events of at least one tracked entity, wherein the scheduled event records of the given user are capable of being scheduled at calendar times that overlap with scheduled shadowed events for the at least one tracked entity; displaying information on the provided scheduled event records and shadowed events for a time period in a view in response to displaying the given user's scheduled event records; receiving selection from the given user to add a selected shadowed event to the given user's scheduled event records; enabling the user to select from the view to add the tracked entity's scheduled event record comprising the selected shadowed event to the given user's scheduled event records in the database, wherein the scheduled event record from the tracked entity added to the given user's scheduled event records are displayed as part of the given user's scheduled event records; and generating a conflict signal if scheduled event records for one user are scheduled for overlapping calendar times, and wherein the conflict signal is not generated if at least one shadowed event record and scheduled event record for which the information is displayed are scheduled for overlapping calendar times.
 2. The method of claim 1, further comprising: displaying information on the shadowed events in a different manner than information on the scheduled event records for the time period is displayed.
 3. The method of claim 2, wherein the information on the shadowed events is displayed as transparent text and the information on the scheduled events are displayed as solid text.
 4. The method of claim 1, wherein information on the shadowed events and scheduled event records are displayed in different calendar panel views.
 5. The method of claim 1, further comprising: displaying further information on the shadowed event in response to user selection of the shadowed event.
 6. The method of claim 1, further comprising: displaying the information on the selected shadowed event as a scheduled event record.
 7. The method of claim 1, further comprising: if the selected shadowed event is scheduled for a calendar time overlapping a calendar time of a scheduled event record, then overriding the scheduled event record for the overlapping time period with the selected shadowed event.
 8. The method of claim 1, wherein the scheduled shadowed event is an event for which payment must be received in order to attend the scheduled shadowed event.
 9. The method of claim 8, further comprising: displaying information enabling the user to selectively submit payment in order to attend the scheduled shadowed event.
 10. The method of claim 8, wherein the shadowed event is a member of a set of events comprising: a theatrical production; movie; sporting event; entertainment; and public speaking engagement.
 11. The method of claim 1, further comprising: maintaining a list of users in the database for which scheduled event records are maintained; and providing one shadowed event to each user in the list, wherein information on the provided shadowed event is displayed by each user on the list when displaying the user information on the scheduled event records and scheduled events.
 12. A system for accessing calendar information comprising: a computer database; means for maintaining scheduled event records for users within the database, including a given user; means for maintaining information for the given user on shadowed events for a tracked entity that are part of the tracked entity's scheduled event records, wherein the tracked entity was selected by the given user; means for providing from the database scheduled event records for the given user and information on shadowed events of at least one tracked entity, wherein the scheduled event records of the given user are capable of being scheduled at calendar times that overlap with scheduled shadowed events for the at least one tracked entity; means for displaying information on the provided scheduled event records and shadowed events for a time period in a view in response to displaying the given user's scheduled event records; means for receiving selection from the given user to add a selected shadowed event to the user scheduled event records; means for enabling the user to select from the view to add the tracked entity's scheduled event record comprising the selected shadowed event to the given user's scheduled event records in the database, wherein the scheduled event record from the tracked entity added to the given user's scheduled event records are displayed as part of the given user's scheduled event records; and means for generating a conflict signal if scheduled event records for one user are scheduled for overlapping calendar times, and wherein the conflict signal is not generated if at least one shadowed event record and scheduled event record for which the information is displayed are scheduled for overlapping calendar times.
 13. The system of claim 12, further comprising: means for displaying information on the shadowed events in a different manner than information on the scheduled event records for the time period is displayed.
 14. The system of claim 13, wherein the information on the shadowed events is displayed as transparent text and the information on the scheduled events are displayed as solid text.
 15. The system of claim 12, wherein information on the shadowed events and scheduled event records are displayed in different calendar panel views.
 16. The system of claim 12, further comprising: means for displaying further information on the shadowed event in response to user selection of the shadowed event.
 17. The system of claim 12, further comprising: means for displaying the information on the selected shadowed event as a scheduled event record.
 18. The system of claim 12, further comprising: means for overriding one scheduled event record overlapping a calendar time of one selected shadowed event.
 19. The system of claim 12, wherein the scheduled shadowed event is an event for which payment must be received in order to attend the scheduled shadowed event.
 20. The system of claim 19, further comprising: means for displaying information enabling the user to selectively submit payment in order to attend the scheduled shadowed event.
 21. The system of claim 19, wherein the shadowed event is a member of a set of events comprising: a theatrical production; movie; sporting event; entertainment; and public speaking engagement.
 22. The system of claim 12, further comprising: means for maintaining a list of users in the database for which scheduled event records are maintained; and means for providing one shadowed event to each user in the list, wherein information on the provided shadowed event is displayed by each user on the list when displaying the user information on the scheduled event records and scheduled events.
 23. An article of manufacture comprising at least one of a hardware device including hardware logic and a computer readable storage medium having computer executable code for accessing calendar information of users in a database for presentation by a personal information manager by: maintaining scheduled event records for users within the database, including a given user; maintaining information for the given user on shadowed events for a tracked entity that are part of the tracked entity's scheduled event records, wherein the tracked entity was selected by the given user; providing from the database scheduled event records for the given user and information on shadowed events of at least one tracked entity, wherein the scheduled event records of the given user are capable of being scheduled at calendar times that overlap with scheduled shadowed events for the at least one tracked entity; displaying information on the provided scheduled event records and shadowed events for a time period in a view in response to displaying the given user's scheduled event records; receiving selection from the given user to add a selected shadowed event to the given user's scheduled event records; enabling the user to select from the view to add the tracked entity's scheduled event record comprising the selected shadowed event to the given user's scheduled event records in the database, wherein the scheduled event record from the tracked entity added to the given user's scheduled event records are displayed as part of the given user's scheduled event records; and generating a conflict signal if scheduled event records for one user are scheduled for overlapping calendar times, and wherein the conflict signal is not generated if at least one shadowed event record and scheduled event record for which the information is displayed are scheduled for overlapping calender times.
 24. The article of manufacture of claim 23, further comprising: displaying information on the shadowed events in a different manner than information on the scheduled event records for the time period is displayed.
 25. The article of manufacture of claim 24, wherein the information on the shadowed events is displayed as transparent text and the information on the scheduled events are displayed as solid text.
 26. The article of manufacture of claim 23, wherein information on the shadowed events and scheduled event records are displayed in different calendar panel views.
 27. The article of manufacture of claim 23, further comprising: displaying further information on the shadowed event in response to user selection of the shadowed event.
 28. The article of manufacture of claim 23, further comprising: displaying the information on the selected shadowed event as a scheduled event record.
 29. The article of manufacture of claim 23, further comprising: if the selected shadowed event is scheduled for a calendar time overlapping a calendar time of a scheduled event record, then overriding the scheduled event record for the overlapping time period with the selected shadowed event.
 30. The article of manufacture of claim 23, wherein the scheduled shadowed event is an event for which payment must be received in order to attend the scheduled shadowed event.
 31. The article of manufacture of claim 30, further comprising: displaying information enabling the user to selectively submit payment in order to attend the scheduled shadowed event.
 32. The article of manufacture of claim 30, wherein the shadowed event is a member of a set of events comprising: a theatrical production; movie; sporting event; entertainment; and public speaking engagement.
 33. The article of manufacture of claim 23, further comprising: maintaining a list of users in the database for which scheduled event records are maintained; and providing one shadowed event to each user in the list, wherein information on the provided shadowed event is displayed by each user on the list when displaying the user information on the scheduled event records and scheduled events. 